Skip to content

Conversation

@slobodanadamovic
Copy link
Contributor

Backport

This will backport the following commits from main to 9.0:

Questions ?

Please refer to the Backport tool documentation

The elastic#127318 changed the behaviour of `client()` to not start a node if there
is none found in the cluster. Which also changed the `getMasterName()`
behaviour to simply fail if there are no nodes instead of starting one.

This is why the `getMasterName()` is failing now. There were no nodes
started because the test scope is set to manually manage master nodes
(`autoManageMasterNodes = false`) without data nodes (`numDataNodes = 0`).

The fix is to actually start the master node instead of attempting to get
the master node name from an empty cluster and depend on a side effect
to actually boostrap a node.

Additionally it awaits for the master node to process all cluster state events
before proceeding, which should hopefully solve the original cause of failures.

Resolves elastic#120964
Resolves elastic#120923

(cherry picked from commit ee6d64a)

# Conflicts:
#	muted-tests.yml
@slobodanadamovic slobodanadamovic self-assigned this Jun 24, 2025
@slobodanadamovic slobodanadamovic added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Jun 24, 2025
@slobodanadamovic slobodanadamovic added auto-backport Automatically create backport pull requests when merged v8.19.1 v8.18.5 labels Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.18.9 v8.19.7 v9.0.9

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants